In light of Civichat's withdrawal,
Public.icon
/emoji/twitter.icon I am tasked with the job of making a system that was created by bureaucrats from all over Japan, written and published in a way that is easy for humans to understand. It's not scaling at all and it's tough. Moreover, there is also the task of assigning codes so that algorithms can interpret it easily...
Hmm, next time I should think about where the bottleneck is and not get stuck. It's meaningless if I don't do it from the center, like Rule as Code, and even then, if the scope is too broad, it will fail. Although MVP is like "we'll do it manually for now, but we'll automate it in the future," it's very difficult if there is no prospect of automation (or it's 10 years away)...
I made mistakes in the product development aspect, and in terms of the domain, there were triple challenges of "the information on the system is updated frequently," "the issuer of the system itself has no incentive to increase usage," and "digitalization is not progressing"... There were many other mistakes in the business, but that's about it.
Problem with business structure
The core was the ability to abstract in the aggregation part, and I think the success factor was that we were able to substitute this part with software. We solved the "making rice from mochi" part of Civichat well.
If you abstract it, the "consulting element" is the main part, where you start with the contract and pick up the needs there, and then abstract it and turn it into a BtoB SaaS. \s\s\sIt cannot be standardized without a logical system like Rule as Code. We had been running civichat-lang as a research and development, but it was difficult to bottom-up Standardization of formal logic description and make it a De facto standard in the current situation. \n\s\s\s[It is necessary to assume the possibility of automation for the future, even if making an MVP is good, and it has been always subjectivized (a bottleneck) that makes mochi from rice in this case.] \n\n\s2. Business sandwiched between end users, citizens, and municipalities as service providers \n\s\sWe needed to form an alliance to provide value as a partner. The product of toC was growing with the PDCA cycle, but we couldn't pivot enough even there. \n\s\s\s> /emoji/twitter.icon This is the number of Civichat users, but at one time there was something like "the number of users quadrupled in a month." However, we are currently stuck due to scalability issues, so I've been thinking lately that there's not much meaning in fitting only toC. \n\s\s\s> https://gyazo.com/9dbc6a8a10add8733d9009759a1ac966\n\s\s\s> @Previous companies, interviews and appearances related to oneselfPrevious companies, interviews and appearances related to oneself.icon November 24, 2021\n\s\sWe should have started with business efficiency of Commissioning of window reception service to a private contractor and develop municipalities SaaS in collaboration with companies handling reception work at the window.\n\n\s3. The information on the system itself is frequently changed (+the format is different for each municipality) \n\s\s\sManaging publicized information continuously was one of the things that municipalities were most weak at. \n\s\s\sThe fact that Architect was weak was always a big problem, and the amount of debt was on a different scale. \n\s\sThe trend of standardizing the format of the CPSV system is also being promoted in Japan, but it has not yet been addressed when it comes to local governments. \n\s\s\sWe had been promoting Civichat portal (BtoG SaaS) as "a platform that can manage systems collectively," but customers did not feel the pain from this issue\n\n\s4. There is no incentive for the system issuing side (municipalities) itself to be used for public systems. \n\s\sMunicipal employees do not necessarily want to solve the problems, they just want to go home and make things easier for themselves. So there was only OMO and other similar services available, but they failed. 5. Overall, there is a bureaucratic mentality and no sense of urgency towards DX. Although it is said to be administrative DX, all they did was pitch events for students. That's it. Problems as a business owner
Struggle with being a jack-of-all-trades
As future options, I can either train myself or work under an excellent PdM to gain momentum.
If I had entrusted the accounting, the money would have been gone.
It was my fault for entrusting it, but as a result, I wasted about 1.5 million yen on two offices (400,000 yen/month) and furniture, security, etc.
There were even chairs that had never been sat on (these were given to Futsupa). If possible, I should have kept in constant communication with investors from an earlier stage.
What remains
What I lost (used) was only time. I don't want to repeat it again, but I have no regrets about what I did.
Network
Learning in terms of skills
Make it public
/emoji/twitter.icon It's not just criticism without praise. It's a story of "do your job" because they say they will introduce a QA tool for B2B SaaS and recommend public systems without domain knowledge, causing the model of objects to collapse, and not disclosing data, and not even presenting a framework for evaluating the effectiveness of PFI and SBI for small governments. ・If you're going to do it, do it smartly.
・At least give us the data.
If you want to shrink welfare and leave it to the private sector (small government), then give money to the private sector.
Use PFI and SIB for that purpose. ...said...
What to do in the future
/emoji/twitter.icon In that sense, I recently feel that "I cannot realize the world line I am aiming for without being an architect in a new field." https://t.co/pfzUylWz8B